This PR was opened by the Changesets release GitHub action. When you're ready to do a release, you can merge this and the packages will be published to npm automatically. If you're not ready to do a release yet, that's fine, whenever you add more changesets to main, this PR will be updated.

⚠️⚠️⚠️⚠️⚠️⚠️

main is currently in pre mode so this branch has prereleases rather than normal releases. If you want to exit prereleases, run changeset pre exit on main.

⚠️⚠️⚠️⚠️⚠️⚠️

Releases

adcontextprotocol@4.0.0-rc.2

Major Changes

• 84ea7b6: Require dotted domains in BrandRef and BrandKey wire schemas, define explicit reserved-domain development exceptions for SDKs, and reserve public registrability plus DNS/SSRF checks for production resolution.

Minor Changes

• 609a3b0: Add buyer and orchestrator agent storyboards: 6 specialisms (buyer-discovery, buyer-activation, buyer-negotiation, buyer-monitoring, buyer-recovery, orchestrator-multi-agent), fixture publisher contract and reference implementation, buyer-orchestrator compliance track with three certification levels, and 10 buyer-specific check kinds.
• ea5c643: Restore the normative constraints canonical-forecast-point dropped from its source twin: the maximum: 1 bounds on viewable_rate and metrics.coverage_rate ranges, and the anyOf requiring standard whenever any viewability value is present. A shared forecast-rate range keeps generated SDK types unambiguous, while a parity contract test compares the twins' resolved viewability schemas and exceptional metric constraints so canonical-pair drift fails CI instead of shipping silently.
• b8ab4fe: Add cursor pagination for truncated get_media_buy_delivery breakdowns on the bounded-enum dimensions: device_type, device_platform, audience, and placement. Previously by_<dim>_truncated: true was a retrieval dead end — there was no protocol-defined way to fetch the dropped rows. Requests can now set reporting_dimensions.<dim>.cursor (reusing the response's new by_<dim>_pagination field, itself the existing pagination-response.json shape already used by get_products) to page through the rest of a truncated breakdown. geo is deliberately excluded — at postal_area granularity it can reach tens of thousands of rows, closer to a bulk-export shape than per-package cursor pagination, and is deferred to the bulk-export/security work tracked in Normative security contract for response/artifact URL handoffs (SSRF + principal-binding) #5669/Epic: large responses & token overhead — handling strategy for AdCP #5666. Closes get_media_buy_delivery: *_truncated breakdowns are retrieval dead-ends #5671.

Patch Changes

• afe8b67: Update the TypeScript SDK checkpoint and current RC.1 guidance to @adcp/sdk@14.0.0-rc.33.
• 4eed58a: Align the AdCP 3.2 release story, SDK compatibility guidance, and Reliable Reporting reference docs with the published RC.1 checkpoint.
• e36e319: Update the 3.2 SDK guidance after the Go RC.1 regeneration merged and its package release entered review.
• 830e306: Serve AdCP 3.2 RC.1 from the public training surface, including Reliable Reporting tools and revision digests, and align the release notes, migration guidance, training, and TypeScript, Python, and Go SDK instructions with the published RC.1 packages.